One thing I'm going to complain about is identifying data types. Is this the only way? It will instantly fail if an application uses some custom data type.

Yeah that is fair. I guess there are two ways to do this:

1. Wait on the NVBit tool for them to fix the issue so we get the sizes of each argument.
2. Or we could ask the user to provide some sort of mapping between data types that go into the kernels and the corresponding sizes.

But ultimately still have to perform some checks on whether the argument is a pointer or not, which could only be confirmed by checking the function signature?

Can you add an else if block at the end and just asssert(0) in it? So if the data type is not enumerated then it will just break and the user would know where to look at. And add a comment there telling the user to add their own data types if reaching the asssert(0).

For the data type identification, we can use the PTX parser in gpgpu-sim to parse it, though it is somewhat hacky.
Update: or we can do this: NVlabs/NVBit#80 (comment)